Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1185

reference
886-tree-1
name
1185
tree-preservation-order

undefined

886-tpo-1
uprn
address-text
point
POINT (-1.018160 50.879262)
geometry
MULTIPOLYGON (((-1.018104 50.879256,-1.018106 50.879267,-1.018114 50.879277,-1.018127 50.879285,-1.018142 50.879291,-1.018160 50.879293,-1.018177 50.879291,-1.018193 50.879286,-1.018206 50.879278,-1.018214 50.879268,-1.018217 50.879257,-1.018215 50.879246,-1.018207 50.879236,-1.018195 50.879228,-1.018179 50.879223,-1.018161 50.879221,-1.018144 50.879222,-1.018128 50.879227,-1.018115 50.879235,-1.018107 50.879245,-1.018104 50.879256)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL